enable client token support #25
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
itsfadnis
reviewed
Feb 28, 2021
| } | ||
|
|
||
| const tld = opts.intakeRegion === 'eu' ? 'eu' : 'com' | ||
| const subdomain = opts.apiKey.startsWith('pub') ? 'browser-http-intake' : 'http-intake' |
There was a problem hiding this comment.
Is there no better way to set the subdomain? Setting in based on the value of apiKey doesn't feel right.
There was a problem hiding this comment.
I am open to a separating the apiKey/clientToken opts, but the subdomains are dependent on the type of key you provide. I.e. sending a client token to http-intake does not result in logs
There was a problem hiding this comment.
@itsfadnis is separating apiKey / clientToken to determine the subdomain ok with you?
I'm interested in this feature
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.